Jediny program ve windows
Otázka od: Matejcek Petr
4. 5. 2004 9:47
DD,
pls nevi nekdo jak udelat, aby po prihlaseni do windows se spustil
muj program v delphi jako jedina mozna aplikace tj obsluha mena sanci
prepnout se nekam jinam, spoustet nic jineho dokonce se ani nezobrazi
nabidka start ani hlavni panel ?
a take jak to vratit zpet ?
PC bude vyuzivano pro jednoucelove rizeni
diky PM
Odpovedá: Jiri Virt
4. 5. 2004 9:39
tusim ze se napsal ten exac do win.ini ..
explore=muj.exe
Jirka Virt
Odpovedá: Ludek ZITA
4. 5. 2004 11:19
On Behalf Of Matejcek Petr
> pls nevi nekdo jak udelat, aby po prihlaseni do windows
> se spustil
> muj program v delphi jako jedina mozna aplikace tj obsluha
> mena sanci
> prepnout se nekam jinam, spoustet nic jineho dokonce se ani nezobrazi
> nabidka start ani hlavni panel ?
> a take jak to vratit zpet ?
Ahoj.
WIN9x :
V system ini zmenit shell=explorer.exe na shell=muj.exe
U W2K nemam prakticke zkusenosti, ale tady mas help k List-Stepu :
win2k,xp
Configuring Windows NT for LiteStep
The most common problem that happens during a LiteStep install on a
Windows
NT machine is that most of the time users
don't have administrative
privileges on their machine and can't use a shell
swapper. There is,
however, a way to get around this.
You will need to modify a few registry entries,
don't be afraid, so fire
up
regedit and lets get started.
HKey_Local_Machine\Software\Windows
NT\CurrentVersion\IniFileMapping\system.ini\boot>SYS:Software\Microsoft\
Windows
NT\CurrentVersion\Winlogon
change this to USR:Software\Microsoft\Windows NT\CurrentVersion\Winlogon
HKey_Current_User\Software\Microsoft\Windows
NT\CurrentVersion\Winlogon>Shell
change the value of Shell to c:\litestep\litestep.exe to add LiteStep.
HKey_Current_User\Software\Microsoft\Windows\CurrentVersion\Explorer\Adv
anced>SeperateProcess
- if this DWORD is set to "1" explorer won't
load as the shell when
triggered inside another shell, if this key is set to "0" it will. This
key
effects LiteStep if you are using Internet Explorer 4 and up, if you
have
an earlier version of Internet Explorer, use a STRING named
DesktopProcess,
with a value of "1" instead of the DWORD. Basically you need this set to
yes if you
don't want to have explorer setting itself as shell everytime
you access it.
Note: You can make LiteStep restart automatically after a crash in
Window
NT. This was taken from the LiteStep b24 Manual written by TheMAN.
"The command SetAsShell makes LiteStep behave as the Official shell and
it
notifies Windows of this fact. This does seem to create some problems
with
Windows at times (especially with IE and quite often when running NT)
and
it has been found that if you do use StepAsShell in your Step.Rc,you
might
have to set the
HKEY_LOCAL_USER\Software\Microsoft\Windows\Current
Version\Explorer\DesktopProcess
key's
value in your registry to 1 to get IE (and Windows) to work
properly.
The only advantage to using SetAsShell is that LiteStep is automatically
started when it crashes, like Explorer normally does. As setting
LiteStep
as the shell seems to create strange problems on different machines, it
is
suggested that you
don't set this value in your Step.Rc. If you do use
SetAsShell and decide to take it out after a while, remember that you
will
have to reboot (not Recycle as is the normal case with a Step.Rc change)
and that you may have to set the
HKEY_LOCAL_USER\Software\Microsoft\Windows\Current
Version\Explorer\DesktopProcess
registry value back to 0 to get everything working properly."
So basically, if you want to try this - take a risk, worst thing that
can
happen is that you will have problems with explorer until you change the
key back.
Configuring Windows 2K for LiteStep
The most common problem that happens during a LiteStep install on a
Windows
NT machine is that most of the time users don't
have administrative
privileges on their machine and
can't use a shell swapper. There is,
however, a way to get around this.
You will need to modify a few registry entries, don't
be afraid, so fire
up
regedit and lets get started.
HKey_Local_Machine\Software\Microsoft\Windows
NT\CurrentVersion\IniFileMapping\system.ini\boot > Shell
change this to USR:Software\Microsoft\Windows NT\CurrentVersion\Winlogon
HKey_Current_User\Software\Microsoft\Windows
NT\CurrentVersion\Winlogon>Shell
change the value of Shell to c:\litestep\litestep.exe to add LiteStep.
HKey_Current_User\Software\Microsoft\Windows\CurrentVersion\Explorer -
Create a New vallue called DesktopProcess and set the Data Field to 1.
HKey_Current_User\Software\Microsoft\Windows\CurrentVersion\Explorer\Bro
wseNewProcess
> - Change this value to "yes", it seems to correct a few problems with
explorer spawning itself as the shell.
Note: You can make LiteStep restart automatically after a crash in
Window
NT. This was taken from the LiteStep b24 Manual written by TheMAN.
"The command SetAsShell makes LiteStep behave as the Official shell and
it
notifies Windows of this fact. This does seem to create some problems
with
Windows at times (especially with IE and quite often when running NT)
and
it has been found that if you do use StepAsShell in your Step.Rc,you
might
have to set the
HKEY_LOCAL_USER\Software\Microsoft\Windows\Current
Version\Explorer\DesktopProcess
key's value in your registry to 1 to get IE (and Windows) to work
properly.
The only advantage to using SetAsShell is that LiteStep is automatically
started when it crashes, like Explorer normally does. As setting
LiteStep
as the shell seems to create strange problems on different machines, it
is
suggested that you don't set this value in your Step.Rc. If you do use
SetAsShell and decide to take it out after a while, remember that you
will
have to reboot (not Recycle as is the normal case with a Step.Rc change)
and that you may have to set the
HKEY_LOCAL_USER\Software\Microsoft\Windows\Current
Version\Explorer\DesktopProcess
registry value back to 0 to get everything working properly."
So basically, if you want to try this - take a risk, worst thing that
can
happen is that you will have problems with explorer until you change the
key back.
Ludek